Added Supabase Connector #6
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Chriztiaan
reviewed
Apr 9, 2025
Chriztiaan
reviewed
Apr 9, 2025
Chriztiaan
reviewed
Apr 9, 2025
Chriztiaan
reviewed
Apr 9, 2025
Chriztiaan
reviewed
Apr 9, 2025
Chriztiaan
reviewed
Apr 9, 2025
Chriztiaan
reviewed
Apr 9, 2025
… and enhance configuration handling
Chriztiaan
previously approved these changes
Apr 10, 2025
Chriztiaan
approved these changes
Apr 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created Supabase connector. Using the configuration in the .env, the user can swop between using the NodeConnector and SupabaseConnector. The Supabase connector implementation needed a work-around for the PATCH event as the dotnet Supabase sdk requires strongly typed property names in the update query. I used my SupabasePatchHelper class to do this by dynamically applying the Set operation to the table; it maps the property by its JSON Property Name (Set in the model class)